🚫 🔍 [Deprecated] Forcepoint CSG via Legacy Agent

🚫 Deprecated: This connector has been deprecated and may be removed in future versions.

🔍 Discovered: This item was discovered by scanning the solution folder but is not listed in the Solution JSON file.

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

Back to Connectors Index


Attribute Value
Connector ID ForcepointCSG
Publisher Forcepoint
Used in Solutions Forcepoint CSG
Collection Method AMA
Connector Definition Files ForcepointCloudSecurityGateway.json

Forcepoint Cloud Security Gateway is a converged cloud security service that provides visibility, control, and threat protection for users and data, wherever they are. For more information visit: https://www.forcepoint.com/product/cloud-security-gateway

Tables Ingested

This connector ingests data into the following tables:

Table Selection Criteria Transformations Ingestion API Lake-Only
CommonSecurityLog Activity == "Blocked"
DeviceProduct in "Email,Web"
DeviceVendor == "Forcepoint CSG"
LogSeverity == "6"
SourceUserID != "Not available"

💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.

Permissions

Resource Provider Permissions:

Setup Instructions

⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.

1. Linux Syslog agent configuration

This integration requires the Linux Syslog agent to collect your Forcepoint Cloud Security Gateway Web/Email logs on port 514 TCP as Common Event Format (CEF) and forward them to Microsoft Sentinel.

2. Implementation options

The integration is made available with two implementations options. 2.1 Docker Implementation

Leverages docker images where the integration component is already installed with all necessary dependencies.

Follow the instructions provided in the Integration Guide linked below.

Integration Guide >

2.2 Traditional Implementation

Requires the manual deployment of the integration component inside a clean Linux machine.

Follow the instructions provided in the Integration Guide linked below.

Integration Guide > 3. Validate connection

Follow the instructions to validate your connectivity:

Open Log Analytics to check if the logs are received using the CommonSecurityLog schema.

It may take about 20 minutes until the connection streams data to your workspace.

If the logs are not received, run the following connectivity validation script:

  1. Make sure that you have Python on your machine using the following command: python -version
  1. You must have elevated permissions (sudo) on your machine

4. Secure your machine

Make sure to configure the machine's security according to your organization's security policy

Learn more >.


Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

Back to Connectors Index